Updating progression of performing computer system maintenance

ABSTRACT

A method, computer program product, and computer system for updating progression of performing computer system management. A computer system receives a log-on of a change implementer onto a managed computer system and searches a change request on a managing computer system. In response to that the change request is found, the computer system receives from the change implementer a command with a current date and time and matches the command to one or more tasks within the change request. In response to determining that the command matches the one or more tasks, the computer system updates start dates and times of the one or more tasks. And, in response to that the one or more tasks are completed, the computer system updates stop dates and times of the one or more tasks.

CROSS REFERENCE TO RELATED APPLICATION

This application is a Continuation Application of pending U.S. patentapplication Ser. No. 13/847,517 filed on Mar. 20, 2013.

FIELD OF THE INVENTION

The present invention relates generally to computer service managementtechnologies and tools, and more particularly to a system and method ofupdating progression of performing computer system management.

BACKGROUND

In computer service management, there is a demand for accuratelymanaging and tracking changes that occur to computer systems. A greatamount of system outages are due to changes in the computingenvironment, where the changes are not planned, authorized, ormistakenly implemented. Since the computer systems are largely managedby processes, there is always the possibility of human errors causingsystem outages.

All currently known solutions to the computer service management arerelated to processes and access restrictions. For example, if a processstates that a change authorization or work record is required beforesystem properties are adjusted, it is the administrator's responsibilityto ensure the change authorization or work record exists. In anotherexample, any user other than a super user has restricted access to acomputer system; in this case, it is the super user's responsibility toensure the process is fulfilled.

SUMMARY

In one aspect, a method for updating progression of performing computersystem management on a managed computer system is provided. The methodcomprises receiving, by an operating system daemon of the managedcomputer, a log on of a change implementer. The method further comprisessending, by the operating system daemon, information of the changeimplementer and the managed computer system, to a managing computersystem. The method further comprises searching, by the managing computersystem, on a change and configuration system on the managing computersystem, configuration items of the managed computer, based on theinformation of the change implementer and the managed computer system.The method further comprises searching, by the managing computer system,on the change and configuration system a change request associated withthe configuration items. The method further comprises determining, bythe managing computer system, whether the change request is found on thechange and configuration system. The method further comprises receiving,by the managing computer system, from the managed computer system, acommand with a current date and time, in response to determining thatthe change request is found on the change and configuration system. Themethod further comprises sending, by the managing computer system, tothe change implementer a warning, in response to determining that thechange request is not found on the change and configuration system. Themethod further comprises searching and matching, by the managingcomputer system, on the change and configuration system, one or moretasks in the change request, the one or more tasks started by thecommand and owned by the change implementer. The method furthercomprises updating, by the managing computer system, on the change andconfiguration system, status of the one or more tasks with start datesand times of the one or more tasks, in response to determining that thecommand matches the one or more tasks found on the change andconfiguration system. The method further comprises updating, by themanaging computer system, on the change and configuration system, thestatus of the one or more tasks with stop dates and times of the one ormore tasks, in response determining that the one or more tasks arecompleted.

In another aspect, a computer program product for managing and trackingcomputer commands associated with a change on a managed computer systemis provided. The computer program product comprises a computer readablestorage medium having program code embodied therewith. The program codeis executable to: receive, by an operating system daemon of the managedcomputer, a log on of a change implementer; send, by the operatingsystem daemon, information of the change implementer and the managedcomputer system, to a managing computer system; search, by the managingcomputer system, on a change and configuration system on the managingcomputer system, configuration items of the managed computer, based onthe information of the change implementer and the managed computersystem; search, by the managing computer system, on the change andconfiguration system a change request associated with the configurationitems; determine, by the managing computer system, whether the changerequest is found on the change and configuration system; receive, by themanaging computer system, from the managed computer system, a commandwith a current date and time, in response to determining that the changerequest is found on the change and configuration system; send, by themanaging computer system, to the change implementer a warning, inresponse to determining that the change request is not found on thechange and configuration system; search and match, by the managingcomputer system, on the change and configuration system, one or moretasks in the change request, the one or more tasks started by thecommand and owned by the change implementer; update, by the managingcomputer system, on the change and configuration system, status of theone or more tasks with start dates and times of the one or more tasks,in response to determining that the command matches the one or moretasks found on the change and configuration system; and update, by themanaging computer system, on the change and configuration system, thestatus of the one or more tasks with stop dates and times of the one ormore tasks, in response determining that the one or more tasks arecompleted.

In yet another aspect, a computer system for managing and trackingcomputer commands associated with a change on a managed computer systemis provided. The computer system comprises one or more processors, oneor more computer readable tangible storage devices, and programinstructions stored on at least one of the one or more computer readabletangible storage devices for execution by at least one of the one ormore processors. The program instructions are executable to receive, byan operating system daemon of the managed computer, a log on of a changeimplementer. The program instructions are executable to send, by theoperating system daemon, information of the change implementer and themanaged computer system, to a managing computer system. The programinstructions are executable to search, by the managing computer system,on a change and configuration system on the managing computer system,configuration items of the managed computer, based on the information ofthe change implementer and the managed computer system. The programinstructions are executable to search, by the managing computer system,on the change and configuration system a change request associated withthe configuration items. The program instructions are executable todetermine, by the managing computer system, whether the change requestis found on the change and configuration system. The programinstructions are executable to receive, by the managing computer system,from the managed computer system, a command with a current date andtime, in response to determining that the change request is found on thechange and configuration system. The program instructions are executableto send, by the managing computer system, to the change implementer awarning, in response to determining that the change request is not foundon the change and configuration system. The program instructions areexecutable to search and match, by the managing computer system, on thechange and configuration system, one or more tasks in the changerequest, the one or more tasks started by the command and owned by thechange implementer. The program instructions are executable to update,by the managing computer system, on the change and configuration system,status of the one or more tasks with start dates and times of the one ormore tasks, in response to determining that the command matches the oneor more tasks found on the change and configuration system. The programinstructions are executable to update, by the managing computer system,on the change and configuration system, the status of the one or moretasks with stop dates and times of the one or more tasks, in responsedetermining that the one or more tasks are completed.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a diagram illustrating a service management system forupdating progression of performing computer system management, inaccordance with an exemplary embodiment of the present invention.

FIG. 2 is a flowchart of the service management system shown in FIG. 1for updating progression of performing computer system management, inaccordance with an exemplary embodiment of the present invention.

FIG. 3 is a diagram of a computer device hosting a managed computersystem or a change and configuration management system on a managingcomputer system, in accordance with an exemplary embodiment of thepresent invention.

DETAILED DESCRIPTION

FIG. 1 is a diagram illustrating service management system 100 forupdating progression of performing computer system management, inaccordance with an exemplary embodiment of the present invention. Inthis exemplary embodiment, service management system 100 comprisesmanaged computer system 110 and change and configuration managementsystem 120. Change and configuration management system 120 is on atleast one managing computer system. In the exemplary embodiment shown inFIG. 1, change management system 121 and configuration management system123 are two primary components of change and configuration managementsystem 120. Change requests on managed computer system 110 are managedby change owner 140 through change and configuration management system120. On change management system 121, change owner 140 creates,approves, and authorizes the changes for managed computer system 110.Change owner 140 manages records of the change requests on changemanagement system 121. The records of change requests includeinformation about which configuration items (CIs) on managed computersystem 110 are to be changed. Within each of the change requests, thereare one or more tasks. Configuration management system 123 is a databasethat stores information of configuration items (CIs) of managed computersystem 110.

Change implementer 130 modifies managed computer system 110. Managedcomputer system 110 comprises OS daemon 115. OS daemon 115 monitorscommands entered by change implementer 130. Monitoring commands usesknown art, for example the audit subsystem for IBM AIX®, the eventregistry in Microsoft Windows®, or other similar systems for otherplatforms. OS daemon 115 sends commands and data to change andconfiguration management system 120, and receives information fromchange and configuration management system 120. Managed computer system110 and change and configuration management system 120 communicateinformation of the change requests, information of tasks within each ofthe change requests, and actual start and stop times of the tasks and/orchange requests being implemented by change implementer 130.

In the exemplary embodiment, OS daemon 115 and change and configurationmanagement system 120 interpret commands entered by change implementer130 of managed computer system 110, and use information of the commandsand information of managed computer system 110 (for example, includingthe userid of the person who logs onto managed computer system 110, thehostname or IP address of managed computer system 110) in combinationwith the current date and time to automatically populate actual startand stop times for a change implemented by change implementer 130 ofmanaged computer system 110.

In service management system 100, the planned changes or change requestson managed computer system 110 are created, approved, and authorized onchange and configuration management system 120 by the change owner 140.Thus, service management system 100 ensures no damaging or disruptivecommands can be issued against managed computer systems 110 unless workrequests for the changes have been generated, approved, and authorized.

In FIG. 1, for the purpose of demonstration, only one managed computersystem (managed computer system 110) is shown in the exemplaryembodiment of service management system 100. It is apparent that servicemanagement system 100 may comprise multiple managed computer systems. Itis also apparent that service management system 100 may comprise one ormore change and configuration management systems.

FIG. 2 is a flowchart of service management system 100 shown in FIG. 1for updating progression of performing computer system management, inaccordance with an exemplary embodiment of the present invention. Atstep 201, change implementer 130 logs onto managed computer system 110to perform a change. At step 203, OS daemon 115 on managed computersystem 110 captures current date and time. The current date and time arebased on the internal clock of managed computer system 110 or a call toa global clock system such as NTP (Network Time Protocol).

At step 205, OS daemon 115 on managed computer system 110 sendsinformation about change implementer 130 and managed computer system 110to change and configuration management system 120. In the exemplaryembodiment, the information about change implementer 130 and managedcomputer system 110 includes the userid of change implementer 130 whologs onto managed computer system 110 and the hostname or IP address ofmanaged computer system 110. For example, to send the information, OSdaemon 115 uses commands “send userid <userid>”, “send hostname<hostname>”, and “send ip address <ip>”.

At step 207, change and configuration management system 120 searchesmatching CIs (configuration items) of managed computer system 110. TheCIs (configuration items) of managed computer system 110 are stored onconfiguration management system 123 on change and configurationmanagement system 120. Change and configuration management system 120searches CIs (configuration items) of managed computer system 110 basedon the hostname or IP address of managed computer system 110.

At step 209, change and configuration management system 120 searches achange request that is associated with the CIs of managed computersystem 110 and has valid status, for example status of “in progress” or“scheduled”. The change request may also be searched by usinginstructions, summary, or details associated with managed computersystem 110.

At decision block 211, change and configuration management system 120determines whether the change request is found. In response to notfinding the change request (No branch of decision block 211), at step213, OS daemon 115 on managed computer system 110 displays a warning.For example, the warning notifies change implementer 130 that no changerequest is found. In other embodiments, OS daemon 115 may redirectchange implementer 130 onto change and configuration management system120 to check status of the change request that change implementer 130 isexpecting to work on.

In response to that the change request is found (YES branch of decisionblock 211), or in response to that OS daemon 115 displays a warning atstep 213, change implementer 130 enters commands at step 215. Thecommands are either implementation commands such as “installp websphere”or interaction commands such as “start task n”.

In response to receiving the commands from change implementer 130, OSdaemon 115 on managed computer system 110, at step 217, sends thecommands with the current date and time to change and configurationmanagement system 120. For example, to send the commands entered bychange implementer 130 with the current date and time, OS daemon 115uses the commands “send command entered”, “send date <current date>”,and “send time <current time>”.

In response to receiving the commands sent by OS daemon 115 at step 217,change and configuration management system 120, at step 221, matches thecommands to one or more tasks. The one or more tasks (for example,installing Websphere®, DB2®, and then some application logic) are withinthe change request. The one or more tasks are implementation tasks thatrequire commands to be run on managed computer system 110. Within one ofthe one or more tasks there are a series of commands (for example“installp websphere”) or key words associated with the one of the one ormore tasks; entering commands or keywords by change implementer 130signals that the one of the one or more tasks has started or iscompleted. At this step, change and configuration management system 120searches implementation tasks to find one or more tasks that are eitherowned directly by change implementer 130 or the group to which changeimplementer 130 belongs. Change and configuration management system 120uses these commands to determine which task or tasks are currently beingworked on. One or more tasks may be found in the change request. At thisstep, change and configuration management system 120 checks whether thecommands match the one or more tasks. If the commands do not match theone or more tasks, change and configuration management system 120determines that the commands are destructive or incorrect commands arerun. In other embodiments, in response to determining that the commandsdo not match the one or more tasks change and configuration managementsystem 120 automatically generates an incident ticket for further followup.

At decision block 223, change and configuration management system 120determines whether the one or more tasks are found. In response todetermining that the one or more tasks are found (YES branch of decisionblock 223), change and configuration management system 120, at step 225,updates the actual start and stop times of the one or more tasks. Atthis step, change and configuration management system 120 determinesscheduled start and stop times at which the tasks are expected to beexecuted. If a command matches one of the one or more tasks andfurthermore matches a command starting the one of the one or more tasks,the current start date and time are automatically populated into actualstart date and time of the command. A similar method is used forpopulating the actual stop time at the end of the one of the one or moretasks.

In response to determining that the tasks are not found (No branch ofdecision block 223), change and configuration management system 120, atdecision block 227, determines whether an incident ticket is requestedby change implementer 130. In response to determining that the incidentticket is requested by change implementer 130 (YES branch of decisionblock 227), change and configuration management system 120 sends therequest for the incident ticket to change owner 140 for change owner'sreview at step 249.

In other embodiments, in response to determining that the tasks are notfound (No branch of decision block 223), change and configurationmanagement system 120 may send a warning to change implementer 130. Ifno task is found, change and configuration management system 120determines that the command has no bearing on the change request. Ineither case, the command is copied to a log entry of the change request.

In response to completion of the change implemented by changeimplementer 130, at step 219, OS daemon 115 logs off change implementer130 from performing computer system management on managed computersystem 110. In response to that OS daemon 115 logs off changeimplementer 130 from performing computer system management, or inresponse to determining that the incident ticket is not requested bychange implementer 130 (NO branch of decision block 227), at step 229,change and configuration management system 120 marks the change requestas completed.

In other embodiments, change and configuration management system 120determines whether a scheduled stop time of a task is reached. Inresponse to determining that the scheduled stop time of the task isreached, change and configuration management system 120 may send changeimplementer 130 a warning (for example, “back out the change now” or“running out of time”), automatically log out change implementer 130,cancel the change request, or mark the change request as “failed”.

In other embodiments, OS daemon 115 or change and configurationmanagement system 120 allows change implementer 130 to override theautomatic detection of an implementation task by using a set of keywords. For example, the keywords includes “start task n” (which signalsthat the change implementer 130 starts task n), “end task n” (whichsignals that the change implementer 130 stops task n), “done” (whichsignals that a current task is complete), and “fail change” (which marksthe change request as failed). OS daemon 115 sends to change andconfiguration management system 120 the keywords entered by changeimplementer 130 using commands, for example, “send start task n” and“send end task n”.

In other embodiments, in response to that a task is started, change andconfiguration management system 120 detects status of the task in thechange request, and changes the status of the task during the progressof implementing the task. For example, change and configurationmanagement system 120 marks the status of the task from “waiting tostart” to “started” and from “started” to “completed”.

In other embodiments, OS daemon 115 on managed computer system 110receives information from change and configuration management system120. For example, OS daemon 115 receives information by using commands:“receive change ID” and “receive task list”.

Referring to FIG. 2, change owner 140 creates a change request at step241. Change owner 140 creates the tasks within the change request atstep 243; each of the tasks has scheduled start and stop dates/times. Atstep 245, change owner 140 authorizes the change request and saves thechange request on change management system 121 which is one of primarycomponents of change and configuration management system 120. Furtherreferring to FIG. 2, change owner 140 views updated task information onchange management system 121 at step 247.

FIG. 3 is a diagram of a computer device hosting managed computer system110 or change and configuration management system 120 on a managingcomputer system, in accordance with an exemplary embodiment of thepresent invention. It should be appreciated that FIG. 3 provides only anillustration of one implementation and does not imply any limitationswith regard to the environment in which different embodiments may beimplemented.

Referring to FIG. 3, the computer device includes processor(s) 320,memory 310, tangible storage device(s) 330, network interface(s) 340,and I/O (input/output) interface(s) 350. In FIG. 3, communications amongthe above-mentioned components of the computer device are denoted bynumeral 300. Memory 310 includes ROM(s) (Read Only Memory) 311, RAM(s)(Random Access Memory) 313, and cache(s) 315.

One or more operating system(s) 331 and one or more computer program(s)333 reside on one or more computer-readable tangible storage device(s)330. For example, on a computer device hosting managed computer system110, one or more computer program(s) 333 include OS daemon 115 (shown inFIG. 1). In the exemplary embodiment, on a computer device hosting themanaging computer system, change and configuration management system 120(including change management system 121 and configuration managementsystem 123, both shown in FIG. 1) resides on one or morecomputer-readable tangible storage device(s) 330. In other embodiments,change management system 121 and configuration management system 123 mayreside on two separate computer devices, respectively.

The computer device further includes I/O interface(s) 350. I/Ointerface(s) 350 allow for input and output of data with externaldevice(s) 360 that may be connected to the computer device. The computerdevice further includes network interface(s) 340 for communicationsbetween the computer device and a computer network.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device, such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network(LAN), a wide area network (WAN), and/or a wireless network. The networkmay comprise copper transmission cables, optical transmission fibers,wireless transmission, routers, firewalls, switches, gateway computersand/or edge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++, and conventionalprocedural programming languages, such as the “C” programming language,or similar programming languages. The computer readable programinstructions may execute entirely on the user's computer, partly on theuser's computer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer, or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider). In some embodiments,electronic circuitry including, for example, programmable logiccircuitry, field-programmable gate arrays (FPGA), or programmable logicarrays (PLA) may execute the computer readable program instructions byutilizing state information of the computer readable programinstructions to personalize the electronic circuitry in order to performaspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture, including instructions which implement aspectsof the function/act specified in the flowchart and/or block diagramblock or blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus, or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the FIGs illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the FIGs. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A method for updating progression of performingcomputer system management on a managed computer system, the methodcomprising: receiving, by an operating system daemon of the managedcomputer system, a log on of a change implementer; receiving, by amanaging computer system from the operating system daemon of the managedcomputer system, information of the change implementer and the managedcomputer system, the information of the change implementer and themanaged computer system including a user ID of the change implementerand a hostname and an IP address of the managed computer system;searching, by the managing computer system, on a change andconfiguration system on the managing computer system, configurationitems of the managed computer system, based on the information of thechange implementer and the managed computer system, wherein the changeand configuration system comprises a database that stores information ofconfiguration items of managed computer system; searching, by themanaging computer system, on the change and configuration system achange request associated with the configuration items and authorized bya change owner; determining, by the managing computer system, whetherthe change request is found in change requests authorized by the changeowner, on the change and configuration system; in response todetermining that the change request is found on the change andconfiguration system, sending, by the managing computer system, to thechange implementer a warning message notifying that the change requestis found; receiving, by the managing computer system, from the changeimplementer of the managed computer system, a command with a currentdate and time entered by the change implementer; sending, by themanaging computer system, to the change implementer a warning messagenotifying that the change request is not found on the change andconfiguration system, in response to determining that the change requestis not found on the change and configuration system; matching, by themanaging computer system, on the change and configuration system, thecommand to one or more tasks that are started by the command and ownedby the change implementer; updating, by the managing computer system, onthe change and configuration system, status of the one or more taskswith start dates and times of the one or more tasks, in response todetermining that the command matches the one or more tasks found on thechange and configuration system; sending, by the change andconfiguration system, to the change implementer on the managed computersystem a warning message notifying that a scheduled stop time for theone or more tasks has reached, in response to determining that thescheduled stop time for the one or more tasks has reached beforecompletion of the one or more tasks; and updating, by the managingcomputer system, on the change and configuration system, the status ofthe one or more tasks with stop dates and times of the one or moretasks, in response to determining that the one or more tasks arecompleted within the scheduled stop time.
 2. The method of claim 1,further comprising: redirecting, by the managing computer system, thechange implementer onto the managing computer system to check status ofthe change request, in response to determining that the change requestis not found on the change and configuration system.
 3. The method ofclaim 1, further comprising: generating, by the managing computersystem, an incident ticket, in response to determining that the commanddoes not match the one or more tasks found on the change andconfiguration system.
 4. The method of claim 1, further comprising:detecting, by the managing computer system, status of the one or moretasks.
 5. The method of claim 1, further comprising: logging off, by themanaging computer system, the change implementer from performingmanagement on the managed computer system, in response to determiningthat the command does not match the one or more tasks found on thechange and configuration system.
 6. The method of claim 1, furthercomprising: capturing, by the operating system daemon of the managedcomputer system, date and time of the log on of the change implementer.7. A computer program product for managing and tracking computercommands associated with a change on a managed computer system, thecomputer program product comprising a computer readable storage mediumhaving program code embodied therewith, the program code executable to:receive, by an operating system daemon of the managed computer system, alog on of a change implementer; receive, by a managing computer systemfrom the operating system daemon of the managed computer system,information of the change implementer and the managed computer system,the information of the change implementer and the managed computersystem including a user ID of the change implementer and a hostname andan IP address of the managed computer system; search, by the managingcomputer system, on a change and configuration system on the managingcomputer system, configuration items of the managed computer system,based on the information of the change implementer and the managedcomputer system, wherein the change and configuration system comprises adatabase that stores information of configuration items of managedcomputer system; search, by the managing computer system, on the changeand configuration system a change request associated with theconfiguration items and authorized by a change owner; determine, by themanaging computer system, whether the change request is found in changerequests authorized by the change owner, on the change and configurationsystem; in response to determining that the change request is found onthe change and configuration system, sending, by the managing computersystem, to the change implementer a warning message notifying that thechange request is found; receive, by the managing computer system, fromthe change implementer of the managed computer system, a command with acurrent date and time entered by the change implementer; send, by themanaging computer system, to the change implementer a warning messagenotifying that the change request is not found on the change andconfiguration system, in response to determining that the change requestis not found on the change and configuration system; match, by themanaging computer system, on the change and configuration system, thecommand to one or more tasks that are started by the command and ownedby the change implementer; update, by the managing computer system, onthe change and configuration system, status of the one or more taskswith start dates and times of the one or more tasks, in response todetermining that the command matches the one or more tasks found on thechange and configuration system; send, by the change and configurationsystem, to the change implementer on the managed computer system awarning message notifying that a scheduled stop time for the one or moretasks has reached, in response to determining that the scheduled stoptime for the one or more tasks has reached before completion of the oneor more tasks; and update, by the managing computer system, on thechange and configuration system, the status of the one or more taskswith stop dates and times of the one or more tasks, in response todetermining that the one or more tasks are completed within thescheduled stop time.
 8. The computer program product of claim 7, furthercomprising the program code executable to: redirect, by the managingcomputer system, the change implementer onto the managing computersystem to check status of the change request, in response to determiningthat the change request is not found on the change and configurationsystem.
 9. The computer program product of claim 7, further comprisingthe program code executable to: generate, by the managing computersystem, an incident ticket, in response to determining that the commanddoes not match the one or more tasks found on the change andconfiguration system.
 10. The computer program product of claim 7,further comprising the program code executable to: detect, by themanaging computer system, status of the one or more tasks.
 11. Thecomputer program product of claim 7, further comprising the program codeexecutable to: log off the change implementer from performing managementon the managed computer system, in response to determining that thecommand does not match the one or more tasks found on the change andconfiguration system.
 12. The computer program product of claim 7,further comprising the program code executable to: capture, by theoperating system daemon of the managed computer system, date and time ofthe log on of the change implementer.
 13. A computer system for managingand tracking computer commands associated with a change on a managedcomputer system, the computer system comprising: one or more processors,one or more computer readable tangible storage devices, and programinstructions stored on at least one of the one or more computer readabletangible storage devices for execution by at least one of the one ormore processors, the program instructions executable to: receive, by anoperating system daemon of the managed computer system, a log on of achange implementer; receive, by a managing computer system from theoperating system daemon of the managed computer system, information ofthe change implementer and the managed computer system, the informationof the change implementer and the managed computer system including auser ID of the change implementer and a hostname and an IP address ofthe managed computer system; search, by the managing computer system, ona change and configuration system on the managing computer system,configuration items of the managed computer system, based on theinformation of the change implementer and the managed computer system,wherein the change and configuration system comprises a database thatstores information of configuration items of managed computer system;search, by the managing computer system, on the change and configurationsystem a change request associated with the configuration items andauthorized by a change owner; determine, by the managing computersystem, whether the change request is found in change requestsauthorized by the change owner, on the change and configuration system;in response to determining that the change request is found on thechange and configuration system, sending, by the managing computersystem, to the change implementer a warning message notifying that thechange request is found; receive, by the managing computer system, fromthe change implementer of the managed computer system, a command with acurrent date and time entered by the change implementer; send, by themanaging computer system, to the change implementer a warning messagenotifying that the change request is not found on the change andconfiguration system, in response to determining that the change requestis not found on the change and configuration system; match, by themanaging computer system, on the change and configuration system, thecommand to one or more tasks that are started by the command and ownedby the change implementer; update, by the managing computer system, onthe change and configuration system, status of the one or more taskswith start dates and times of the one or more tasks, in response todetermining that the command matches the one or more tasks found on thechange and configuration system; send, by the change and configurationsystem, to the change implementer on the managed computer system awarning message notifying that a scheduled stop time for the one or moretasks has reached, in response to determining that the scheduled stoptime for the one or more tasks has reached before completion of the oneor more tasks; and update, by the managing computer system, on thechange and configuration system, the status of the one or more taskswith stop dates and times of the one or more tasks, in response todetermining that the one or more tasks are completed within thescheduled stop time.
 14. The computer system of claim 13, furthercomprising the program instructions executable to: redirect, by themanaging computer system, the change implementer onto the managingcomputer system to check status of the change request, in response todetermining that the change request is not found on the change andconfiguration system.
 15. The computer system of claim 13, furthercomprising the program instructions executable to: generate, by themanaging computer system, an incident ticket, in response to determiningthat the command does not match the one or more tasks found on thechange and configuration system.
 16. The computer system of claim 13,further comprising the program instructions executable to: detect, bythe managing computer system, status of the one or more tasks.
 17. Thecomputer system of claim 13, further comprising the program instructionsexecutable to: log off the change implementer from performing managementon the managed computer system, in response to determining that thecommand does not match the one or more tasks found on the change andconfiguration system.
 18. The computer system of claim 13, furthercomprising the program instructions executable to: capture, by theoperating system daemon of the managed computer system, date and time ofthe log on of the change implementer.